Communication system and server

ABSTRACT

A SOAP-SIP adapter  2  establishes a session with the terminals  5   b  and  5   c  in accordance with a SIP. At this time, the SOAP-SIP adapter  2  sends an INVITE message including its own IP address and port number to the terminals  5   b  and  5   c . Each terminal  5   b,    5   c  sends a 200 OK including its own IP address and port number to the SOAP-SIP adapter  2 . The SOAP-SIP adapter  2  stores correspondingly the IP address and port number of each terminal  5   b,    5   c  in a memory. The SOAP-SIP adapter  2  transfers a media stream received from each terminal  5   b,    5   c  to the destination of the corresponding IP address and port number by referring to the memory. Also, a pseudo RBT is sent to the terminal A 5   b  from establishing the session with the terminal A 5   b  till establishing the session with the terminal B 5   c  to prevent a silent state.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

Japan Priority Application 2009-057473, filed Mar. 11, 2009 includingthe specification, drawings, claims and abstract, is incorporated hereinby reference in its entirety. This application is a Continuation of U.S.application Ser. No. 12/688,802, filed Jan. 15, 2010, incorporatedherein by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a communication system and a server,and more particularly to a communication system and a server with anaction points connection method in the next generation network.

2. Description of the Related Art

In recent years, various examinations for the communication network ofthe next generation with the common carrier using an Internet Protocol(IP) technique have been vigorously made. The next generationcommunication network of this kind is called an Next Generation Network(NGN). In the NGN, a method for establishing a session between theserver and the client to be communicated and managing the band for eachsession is often employed. Also, in the NGN, a session control protocolfor use in reserving the band is a Session Initiation Protocol (SIP),for example.

Also, there has been disclosed another technique in which when a clientapparatus mounting no control protocol for the session for reserving theband communicates in a band assured network, a session substitutingdevice establishes the session for reserving the band in the bandassured network, instead of the client apparatus (e.g., refer toJP-A-2008-78878).

Also, a Simple Object Access Protocol (SOAP) for exchanging theinformation between applications has been known.

SUMMARY OF THE INVENTION

In the NGN, it is required that the IP addresses for establishing thesignaling channel and the data channel are the same. Therefore, there isa problem that it is impossible to substitute the establishment of thedata channel between two parties (first connection terminal and secondconnection terminal) to be communicated such as the conventional 3rdParty Call Control (3PCC) service flow. Also, there is another problemin the 3PCC service flow that when the telephone communication is madebetween the first connection terminal and the second connection terminalby firstly establishing the session between an apparatus with the 3PCCand the first connection terminal and then establishing the sessionbetween the apparatus with the 3PCC and the second connection terminal,the first connection terminal is placed in a silent state at the stagewhere the establishment of the session with the first connectionterminal is completed and the establishment of the session with thesecond connection terminal is started. Also, most of the existentapplication terminals have no SIP for reserving the communication bandin the NGN, in which there is another problem that the communication onthe NGN is impossible.

In view of the above-mentioned problems, it is an object of the presentinvention to provide a communication system and a server fortransferring the data between two parties (first connection terminal andsecond connection terminal) to be communicated in the NGN with assuredcommunication quality. Also, it is another object of the invention toprovide a 3PCC service on the NGN with assured communication quality. Itis still another object of the invention to prevent the first connectionterminal from being placed in the silent state in establishing thesession with the second connection terminal after establishing thesession with the first connection terminal in the 3PCC service flow.

Further, it is another object of the invention to provide acommunication system and a server in which the terminal can reserve thecommunication band on the NGN with the partner terminal without beingaware of the SIP and communicate on the NGN with reserved band throughthe steady operation on the already existent internet after reservingthe communication band. Also, it is another object of the invention tomount an interface capable of establishing many sessions on an SOAP-SIPadapter to make it possible to establish hundreds to thousands ofsessions.

According to the first solving means of present invention, there isprovided a communication system having a first server, a device formaking an establishment of connection with said first server in a SIPprotocol, and a first terminal for communicating with said first server,wherein said first server comprises:

an interface for receiving a connection request message;

a processing part for making the establishment of connection with saiddevice in said SIP protocol in accordance with received connectionrequest message; and

a first transfer control part for transferring data received from saidfirst terminal to said device after the establishment of connection bysaid processing part.

According to the second solving means of present invention, there isprovided a server in a communication system which has said server, adevice for making an establishment of connection with said server in aSIP protocol, and a terminal for communicating with said server, saidserver comprising:

an interface for receiving a connection request message;

a processing part for making the establishment of connection with saiddevice in said SIP protocol in accordance with received connectionrequest message; and

a first transfer control part for transferring data received from saidfirst terminal to said device after the establishment of connection bysaid processing part.

According to the present invention, it is possible to provide acommunication system and a server for transferring the data between twoparties (first connection terminal and second connection terminal) to becommunicated in the NGN with assured communication quality. According tothe invention, it is possible to provide a 3PCC service on the NGN withassured communication quality. According to the invention, it ispossible to prevent the first connection terminal from being placed inthe silent state in establishing the session with the second connectionterminal after establishing the session with the first connectionterminal in the 3PCC service flow.

Further, according to the invention, it is possible to provide acommunication system and a server in which the terminal can reserve thecommunication band on the NGN with the partner terminal without beingaware of the SIP and communicate on the NGN with reserved band throughthe steady operation on the already existent internet after reservingthe communication band. According to the invention, it is possible tomount an interface capable of establishing many sessions on an SOAP-SIPadapter to make it possible to establish hundreds to thousands ofsessions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an explanatory view showing a configuration example of acommunication network according to a first embodiment.

FIG. 2 is an explanatory view showing a configuration example of anSOAP-SIP adapter 2 according to the first embodiment.

FIG. 3A is an explanatory view showing one example of the organizationof a session information table 2010 in the SOAP-SIP adapter 2 accordingto the first embodiment.

FIG. 3B is an explanatory view showing one example of the organizationof a call participant information table 2020 in the SOAP-SIP adapter 2according to the first embodiment.

FIG. 3C is an explanatory view showing one example of the organizationof a terminal information table 2030 in the SOAP-SIP adapter 2 accordingto the first embodiment.

FIG. 3D is an explanatory view showing one example of the organizationof a media stream control information table 2040 in the SOAP-SIP adapter2 according to the first embodiment.

FIG. 4 is an explanatory view showing a configuration example of acommunication network according to a second embodiment.

FIG. 5 is an explanatory view showing a configuration example of anSOAP-SIP adapter 6 according to the second embodiment.

FIG. 6A is an explanatory view showing one example of the organizationof a connection information table 5010 in the SOAP-SIP adapter 6 aaccording to the second embodiment.

FIG. 6B is an explanatory view showing one example of the organizationof a terminal information table 5020 in the SOAP-SIP adapter 6 aaccording to the second embodiment.

FIG. 6C is an explanatory view showing one example of the organizationof a media stream control information table 5030 in the SOAP-SIP adapter6 a according to the second embodiment.

FIG. 7 is a flowchart for explaining the generation of a sessionID/connection ID in the SOAP-SIP adapter.

FIG. 8 is a flowchart for explaining the operation in receiving a callstart request in the SOAP-SIP adapter 2 according to the firstembodiment.

FIG. 9 is a flowchart for explaining the operation in receiving a callinformation (session information) request in the SOAP-SIP adapter 2according to the first embodiment.

FIG. 10 is a flowchart for explaining the operation in receiving a callparticipant information request in the SOAP-SIP adapter 2 according tothe first embodiment.

FIG. 11 is a flowchart for explaining the operation in receiving a callend request in the SOAP-SIP adapter 2 according to the first embodiment.

FIG. 12 is a sequence chart (1) for explaining a 3PCC service procedureaccording to the first embodiment.

FIG. 13 is a sequence chart (2) for explaining the 3PCC serviceprocedure according to the first embodiment.

FIG. 14 is a sequence chart (3) for explaining the 3PCC serviceprocedure according to the first embodiment.

FIG. 15 is a sequence chart (4) for explaining the 3PCC serviceprocedure according to the first embodiment.

FIG. 16 is a flowchart for explaining the operation in receiving aconnection start request in the SOAP-SIP adapter 6 according to thesecond embodiment.

FIG. 17 is a flowchart for explaining the operation in receiving aconnection information request in the SOAP-SIP adapter 6 according tothe second embodiment.

FIG. 18 is a flowchart for explaining the operation in receiving aconnection end request in the SOAP-SIP adapter 6 according to the secondembodiment.

FIG. 19 is a sequence chart (1) for explaining an NGN connection serviceprocedure according to the second embodiment.

FIG. 20 is a sequence chart (2) for explaining the NGN connectionservice procedure according to the second embodiment.

FIG. 21A is an explanatory view showing one example of the organizationof a connection information table 6010 in the SOAP-SIP adapter 6 aaccording to the second embodiment.

FIG. 21B is an explanatory view showing one example of the organizationof a terminal information table 6020 in the SOAP-SIP adapter 6 baccording to the second embodiment.

FIG. 21C is an explanatory view showing one example of the organizationof a media stream control information table 6030 in the SOAP-SIP adapter6 b according to the second embodiment.

FIG. 22 is a flowchart for explaining the operation in receiving a callincoming notice in the SOAP-SIP adapter 6 according to the secondembodiment.

FIG. 23 is a flowchart for explaining the operation in receiving adisconnect notice in the SOAP-SIP adapter 6 according to the secondembodiment.

FIG. 24 is a configuration diagram of a web server 1.

DETAILED DESCRIPTION OF THE INVENTION 1. First Embodiment NetworkConfiguration

FIG. 1 is an explanatory view showing a configuration example of acommunication network according to a first embodiment.

This communication network (system) comprises a Web server 1, anSOAP-SIP adapter 2, a SIP server 3, and an Home Gateway (HGW) 4 a, 4 b,for example. The SIP server 3 is installed in an NGN N2, for example.

The Web server 1 communicates with the SOAP-SIP adapter 2. Also, the Webserver 1 communicates via a network such as internet N1 with a terminal5 a. The SOAP-SIP adapter 2 communicates via the NGN N2 and the HGW 4 awith a terminal A5 b. The SOAP-SIP adapter 2 and a terminal B5 c havealso the same configuration.

FIG. 2 is an explanatory view showing a configuration example of theSOAP-SIP adapter 2 according to the first embodiment.

The SOAP-SIP adapter 2 comprises a processor (hereinafter CPU) 2001, aninterface (hereinafter IF) 2003 a, 2003 b, and a memory 2004, forexample. The memory 2004 has an SOAP control part 2101, a SPCC modulepart 2102, a media stream control part 2103, and a SIP control part2104. The SPCC module part 2102 has a session information table 2010,and the media stream control part 2103 has a media stream controlinformation table 2040. The session information table 2010 has a callparticipant information table 2020 and a terminal information table2030.

The CPU 2001 performs each processing in the SOAP-SIP adapter 2. TheSOAP control part 2101, the 3PCC module part 2102, the media streamcontrol part 2103 and the SIP control part 2104 on the memory 2004 areperformed by the CPU 2001. The IF 2003 is interface for making thecommunication via a line 2002 with the Web server 1 and the NGN N2.

FIG. 3A is an explanatory view showing one example of the organizationof the session information table 2010 in the SOAP-SIP adapter 2according to the first embodiment.

The session information table 2010 stores, associated with a session ID2011, a session state 2012, a call participant state 2020, and theterminal information 2030, for example.

The session ID 2011 is a session identifier corresponding to aconnection request from the Web server 1. The session ID 2011 identifiesthe communication between the terminal A5 b and the terminal B5 c. Thesession state 2012 indicates the state of session designated by thesession ID 2011. The session state 2012 stores an “Initial (initialstate)”, a “Connected (connected state)”, or a “Terminated (terminatedstate)”, for example. The call participant state 2020 corresponds to thecall participant information table 2020. The details of the callparticipant information table 2020 will be described below. The terminalinformation 2030 corresponds to the terminal information table 2030. Theterminal information 2030 is stored for each terminal. In an illustratedexample, the terminal information (for Client A) 2030_A corresponding tothe terminal A5 b and the terminal information (for Client B) 2030_Bcorresponding to the terminal B5 c are stored. The details of theterminal information table 2030 will be described below.

FIG. 3B is an explanatory view showing one example of the organizationof the call participant information table 2020 in the SOAP-SIP adapter 2according to the first embodiment.

The call participant information table 2020 stores, for each terminal, aURI 2021, a call state 2022 and a start time (clock) 2023, for example.

The URI 2021 indicates a SIP-URI corresponding to each user. The callstate 2022 indicates the state of session of the SIP between theSOAP-SIP adapter 2 and each terminal 5 b, 5 c. The call state 2022stores a “Call Participant Initial (Initial state)”, a “Call ParticipantConnected (connected state)” or a “Call Participant Terminated(terminated state)”, for example. The start time 2023 indicates the timewhen the SOAP-SIP adapter 2 establishes the session of the SIP for eachterminal 5 b, 5 c.

FIG. 3C is an explanatory view showing one example of the organizationof the terminal information table 2030 in the SOAP-SIP adapter 2according to the first embodiment.

The terminal information table 2030 stores the parameters for use in theSIP, for example. The terminal information table 2030 stores a handlevalue 2031, a session ID 2032, a terminal state 2033, a Role 2034, thesend Session Description Protocol (SDP) information 2035, the recv SDPinformation 2036, a From URI 2037, and a To URI 2038, for example.

The handle value 2031 is the information for identifying the session ofthe SIP between the SOAP-SIP adapter 2 and the terminal 5 b and thesession of the SIP between the SOAP-SIP adapter 2 and the terminal B5 c.The session ID 2032 corresponds to the session ID 2011 of the sessioninformation table 2010. The terminal state 2033 indicates the state tillestablishing the session between the SOAP-SIP adapter 2 and eachterminal 5 b, 5 c. The terminal state 2033 accepts an “Initial (initialstate)”, a “Connect Wait (state waiting for a ‘response’)”, a “CallComplete (state accepting the ‘response’ and establishing the sessionwith the UA, a “Close Wait (state waiting for a ‘disconnect completenotice’)”, and a “Closed (terminated state)”, for example. The “Initial”and the “Connect Wait” correspond to the “Call Participant Initial” ofthe call state 2022 stored in the call participant information table2020. Also, the “Call Complete” and the “Close Wait” correspond to the“Call Participant Connected” of the call state 2022 stored in the callparticipant information table 2020. The “Close Wait” corresponds to the“Call Participant Terminated” of the call state 2022.

The Role 2034 is the information indicating the call outgoing side orcall incoming side. The send SDP information 2035 includes the IPaddress and the port number of the SOAP-SIP adapter 2, for example. Therecv SDP information 2036 includes the IP address and the port number ofthe terminal A5 b or terminal B5 c, for example. The From URI 2037indicates the sender URI of a SIP message sent by the SOAP-SIP adapter2. The From URI 2037 is the SIP-URI of the SOAP-SIP adapter 2, forexample. The To URI 2038 indicates the destination URI of SIP messagesent by the SOAP-SIP adapter 2. The To URI 2038 is the SIP-URI of theterminal A5 b or terminal B5 c, for example.

FIG. 3D is an explanatory view showing one example of the organizationof the media stream control information table 2040 in the SOAP-SIPadapter 2 according to the first embodiment.

The media stream control information table 2040 stores, associated witha session ID 2041, a media stream sending/receiving IP address 2042, amedia stream sending/receiving port number 2043, a partner IP address(1) 2044, a partner port number (1) 2045, a partner IP address (2) 2046,and a partner port number (2) 2047, for example.

The session ID 2041 corresponds to the session ID 2011 of the sessioninformation table 2010. The media stream sending/receiving IP address2042 and the media stream sending/receiving port number 2043 are the IPaddress and the port number of the IF 2003 for use when the SOAP-SIPadapter 2 transfers the media stream. The pairs of the partner IPaddress (1) 2044 and the partner port number (1) 2045 and the partner IPaddress (2) 2046 and the partner port number (2) 2047 designate thedestination of transferring the media stream. For example, in the casewhere the sender of the media stream corresponds to the partner IPaddress (1) 2044 and the partner port number (1) 2045, the media streamis transferred to the corresponding destination with the partner IPaddress (2) 2046 and the partner port number (2) 2047. In the case wherethe sender of the media stream corresponds to the partner IP address (2)2046 and the partner port number (2) 2047, the media stream istransferred to the corresponding destination with the partner IP address(2) 2044 and partner port number (1) 2045 in the same manner. In anillustrated example, the partner IP address (1) 2044 and the partnerport number (1) 2045 designate the IP address and the port number of theterminal A5 b, and the partner IP address (2) 2046 and the partner portnumber (2) 2047 designate the IP address and the port number of theterminal B5 c.

FIG. 24 is a configuration diagram of the web server 1.

The web server 1 comprises a processing part 100, an input part 110, adisplay part 120, a storage part 130, and a communication interface 140,for example. The input part 110 receives the input of a Session ID orthe input of a user identifier, for example. The display part 120displays the user identifier and the SIP-URI. The storage part 130stores the received Session ID, for example. The communication interface140 is the interface for communicating with the SOAP-SIP adapter 2, forexample. The processing part 100 performs various kinds of processing inthe web server 1.

(Operation)

FIG. 12 is a sequence chart for explaining a 3PCC service procedureaccording to the first embodiment.

FIG. 7 is a flowchart for explaining the generation of a sessionID/connection ID in the SOAP-SIP adapter. The connection ID is used inthe second embodiment. FIG. 8 is a flowchart for explaining theoperation in receiving a call start request in the SOAP-SIP adapter 2according to the first embodiment.

According to this embodiment, it is possible to provide the 3PCC serviceon the NGN with the assured communication quality.

The flow up to the 3PCC service is the following (a) to (c). (a)Establishment of the session between the SOAP-SIP adapter 2 and thefirst connection terminal A5 b. (b) Establishment of the session betweenthe SOAP-SIP adapter 2 and the second connection terminal B5 c. (c)Telephone communication between the first connection terminal A5 b andthe second connection terminal B5 c. However, there is a problem thatthe first connection terminal A5 b is placed in a silent state at thestage where (a) is completed and (b) is started. Thus, a Ringing BackTone, (RBT, connection maintaining message) is artificially sent fromthe SOAP-SIP adapter 2 to the first connection terminal A5 b to resolvethis problem.

Also, in the NGN, there is a necessary condition that the IP addressesfor establishing the signaling channel and the data channel are thesame, resulting in a problem that it is impossible to vicariouslyexecute the establishment of data channel between two parties (the firstconnection terminal A5 b and the second connection terminal B5 c) to becommunicated as in the conventional SPCC service flow. Thus, in thisembodiment, the data from the first connection terminal A5 b is receivedby the SOAP-SIP adapter 2 and transferred to the second connectionterminal B5 c. The data from the second connection terminal B5 c isreceived by the SOAP-SIP adapter 2 and transferred to the firstconnection terminal A5 b. Also, the SOAP-SIP adapter 2 creates the mediastream control information table 2040 for implementing the abovetransfer.

The procedure of this embodiment will be described below in accordancewith the sequence charts and the flowcharts.

First of all, the user of the third party logs into the Web server 1 byoperating the terminal 5 a. The Web server 1 inputs the user identifiersof the users to communicate (e.g., user names of two partiescorresponding to the terminal A5 b and the terminal B5 c) from theterminal 5 a. For example, the Web server 1 may select the users of twoparties to communicate through the operation of the user in accordancewith the screen displayed for the terminal 5 a that logs in.

The Web server 1 sends an SOAP make Call Session Request (connectionrequest) to the SOAP-SIP adapter 2 (S1). The SOAP make Call SessionRequest includes the SIP-URI corresponding to each of the user of twoparties to be connected. For example, the Web server 1 acquires theSIP-URI corresponding to the input user identifier, because the useridentifier and the SIP-URI of the user are associated and prestored. TheWeb sever 1 generates the SOAP make Call Session Request including theacquired SIP-URI, and sends it to the SOAP-SIP adapter 2.

The SOAP-SIP adapter 2 starts the connection to each terminal 5 b, 5 ccorresponding to the SIP-URI included in the received SOAP make CallSession Request, and sends an SOAP make Call Session Response includingthe session ID generated in the SOAP-SIP adapter 2 (S2 to S15). Thedetailed operation of the steps S2 to S15 in the SOAP-SIP adapter 2 willbe described below.

The SOAP control part 2101 of the SOAP-SIP adapter 2 receives the SOAPmake Call Session Request, and sends a connection request to the SPCCmodule part 2102 (S2). This connection request can be generated inaccordance with an appropriate protocol for use in the SOAP-SIP adapter2, based on the received SOAP make Call Session Request, for example,and includes the SIP-URI within the SOAP make Call Session Request.

The SPCC module part 2102 receives the connection request (7001, 8001),and generates a session ID (8002). Referring to FIG. 7, the generationof the session ID will be described below.

The SPCC module part 2102 receives the connection request and generatesthe random number value (7002). The 3PCC module part 2102 judges whetheror not the generated random number value is already registered in thesession ID 2011 of the session information table 2010 (7003). If thegenerated random number value is already registered (i.e., alreadyused), the 3PCC module part 2102 returns to step 7002 to repeat thesubsequent processing. On the other hand, if the generated random numbervalue is not registered, the SPCC module part 2102 stores the generatedsession ID in the session information table 2010 (7004). Further, theSPCC module part 2102 sets the session state 2012 of the sessioninformation table 2010 to “Initial (initial state)”.

Also, the 3PCC module part 2102 stores the SIP-URI included in thereceived connection request in the call participant information table2020. In an example of the call participant information table 2020 asshown in FIG. 3B, the SIP-URI (see 2020_A) of the terminal A5 b and theSIP-URI (see 2020_B) of the terminal B5 c are stored. The 3PCC modulepart 2102 sets the call state 2022 corresponding to each terminal 5 b, 5c of the call participant information table 2020 to “Call ParticipantInitial (initial state)”.

Moreover, the 3PCC module part 2102 stores the terminal information ofthe terminal A5 b and the terminal B5 c. More specifically, the 3PCCmodule part 2102 stores the generated session ID in the terminalinformation table 2030, associated with each terminal 5 b, 5 c. Also,the 3PCC module part 2102 stores each SIP-URI included in the receivedconnection request in the To URI 2038 corresponding to each terminal 5b, 5 c of the terminal information table 2030. The 3PCC module part 2102sets the terminal state 2032 corresponding to each terminal 5 b, 5 c ofthe terminal information table 2030 to “Initial (initial state)”. The3PCC module part 2102 sets the information indicating the call outgoingside or call incoming side to the Role 2033 corresponding to eachterminal 5 b, 5 c of the terminal information table 2030. It can beappropriately decided which of the terminals 5 b and 5 c is the calloutgoing side. Also, the 3PCC module part 2102 stores the IP address andthe port number of the SOAP-SIP adapter 2 in the send SDP information2035 of the terminal information table 2030. Also, the 3PCC module part2102 stores the SIP-URI of the SOAP-SIP adapter 2 in the From URI 2037corresponding to each terminal 5 b, 5 c of the terminal informationtable 2030. The SIP-URI, the IP address and the port number of theSOAP-SIP adapter 2 are prestored in the appropriate storage part.

The 3PCC module part 2102 generates a connection request successresponse, and sends it to the SOAP control part 2101 (S3, 8011). Theconnection request success response includes the generated session ID.The SOAP control part 2101 receives the connection request successresponse, and sends an SOAP make Call Session Response (connectionrequest success response) to the Web server 1 (S4, 8012). The SOAP makeCall Session Response includes the generated session ID, and isgenerated in accordance with the SOAP, based on the received connectionrequest success response. The Web server 1 receives the SOAP make CallSession Response, and stores the session ID included in the receivedSOAP make Call Session Response in the appropriate storage part.

If the generation of the session ID fails at step 8002, the 3PCC modulepart 2102 generates a connection request failure response (errorresponse message) (8013), and sends it to the SOAP control part 2101.The SOAP control part 2101 receives the connection request failureresponse, and sends an SOAP make Call Session Response indicating theconnection request failure to the Web server 1 (8012).

Next, the session between the SOAP-SIP adapter 2 and the terminal A5 bis established.

More specifically, the SPCC module part 2102 acquires a media streamcontrol/transfer port (8003). The 3PCC module part 2102 sends a calloutgoing request (A) for the terminal A5 b to the SIP control part 2104(S5, 8004). For example, the 3PCC module part 2102 sends the calloutgoing request including the send SDP information 2035, the From URI2037 and the To URI 2038 corresponding to the terminal A5 b stored inthe terminal information table 2030 to the SIP control part 2104. Also,the 3PCC module part 2102 stores the current time as one example in thestart time 2023 corresponding to the terminal A5 b of the callparticipant information table 2020. In an example of the callparticipant information table 2020 as shown in FIG. 3B, “2008.10.2210:30.30” is stored. The start time 2023 is not limited to the currenttime, but may be the appropriate time indicating the start of sessionwith the terminal A5 b.

The SIP control part 2104 sends an INVITE message (A) to the terminal A5b in accordance with the To URI included in the call outgoing request(A) (S6). The INVITE message (A) includes at least the send SDPinformation, the From URI, and the To URI included in the received calloutgoing request, for example. Also, the SIP control part 2104 generatesa handle value identifying the session with the terminal A5 b.

The terminal A5 b receives the INVITE message (A), and stores the IPaddress and the port number of the SOAP-SIP adapter 2 included in thesend SDP information of the received INVITE message (A) in theappropriate storage part. The stored IP address and port number are usedin sending the media stream, for example. Also, the terminal A5 bgenerates the recv SDP information including its own IP address and portnumber and sends a 200 OK (A) of the SIP including the generated SDPinformation to the SOAP-SIP adapter 2 (S7). The SIP control part 2104 ofthe SOAP-SIP adapter 2 receives the 200 OK (A) and sends an ACK (A) ofthe SIP to the terminal A5 b (S8).

The SIP control part 2104 sends a response notice (A) to the SPCC modulepart 2102 (S9, 8005). The response notice (A) includes the handle valuegenerated at step S6 and the recv SDP information of the terminal A5 bincluded in the 200 OK received at step S7, for example. The 3PCC modulepart 2102 stores, associated with the terminal A5 b, the handle valueand the recv SDP information included in the received response notice(A) in the terminal information table 2030. The handle value may bestored at an appropriate timing from step S6 to step S8. The 3PCC modulepart 2102 updates the terminal state 2033 corresponding to the terminalA5 b of the terminal information table 2030 to “Call Complete (sessionestablished state)”. Also, the 3PCC module part 2102 updates the callstate 2022 corresponding to the terminal A5 b of the call participantinformation table 2020 to “Call Participant Connected (connectedstate)”. The terminal state 2033 may be appropriately updated uponsending or receiving the SIP message (e.g., 200 OK and so on), forexample.

Also, the 3PCC module part 2102 sends the generated session ID, the IPaddress and port number of the SOAP-SIP adapter 2, and the IP addressand port number of the terminal A5 b included in the received recv SDPinformation to the media stream control part 2103. The media streamcontrol part 2103 stores the received information in the media streamcontrol information table 2040. For example, the media stream controlpart 2103 stores the received IP address and port number of the SOAP-SIPadapter 2 at the media stream sending/receiving IP address 2042 and themedia stream sending/receiving port number 2043, and stores the receivedIP address and port number of the terminal A5 b at the partner IPaddress (1) 2044 and the partner port number (1) 2045. Also, the mediastream control part 2103 stores the received session ID.

The 3PCC module part 2102 sends a pseudo RBT sending request to themedia stream control part 2103 (S101). The media stream control part2103 receives the pseudo RBT sending request, and sends the pseudo RBTto the terminal A5 b in accordance with a Real-time Transport Protocol(RTP), for example (S10, 8006). The media stream control part 2103 mayuse an announcement of calling the partner or appropriate music, forexample, as the pseudo RBT. In this embodiment, the terminal A5 b isprevented from being in silent state at the stage where theestablishment of session with the terminal A5 b is completed and theestablishment of session with the terminal B5 c is started. This pseudoRBT can continue to be sent until a stop request is made as will bedescribed later.

Next, the session between the SOAP-SIP adapter 2 and the terminal B5 cis established.

The 3PCC module part 2102 sends a call outgoing request (B) for theterminal B5 c to the SIP control part 2104 (S11, 8007). For example, the3PCC module part 2102 sends the call outgoing request including the sendSDP information 2035, the From URI 2037 and the To URI 2038corresponding to the terminal B5 c stored in the terminal informationtable 2030 to the SIP control part 2104. Also, the 3PCC module part 2102stores the current time in the start time 2023 corresponding to theterminal B5 c of the call participant information table 2020. In anexample of the call participant information table 2020 as shown in FIG.3B, “2008.10.22 10:30.45” is stored.

The SIP control part 2104 sends an INVITE message (B) to the terminal B5c in accordance with the To URI included in the call outgoing request(A) (S12). The INVITE message (B) includes at least the send SDPinformation, the From URI, and the To URI included in the received calloutgoing request, for example. Also, the SIP control part 2104 generatesa handle value identifying the session with the terminal B5 c.

The terminal B5 c receives the INVITE message (B), and stores the IPaddress and port number of the SOAP-SIP adapter 2 included in the sendSDP information of the received INVITE message (B) in the appropriatestorage part. Also, the terminal B5 c generates the recv SDP informationincluding its own IP address and port number and sends a 200 OK (B)including the generated recv SDP information to the SOAP-SIP adapter 2(S13). The SIP control part 2104 of the SOAP-SIP adapter 2 receives the200 OK (B) and sends an ACK (B) to the terminal B5 c (S14).

The SIP control part 2104 sends a response notice (B) to the SPCC modulepart 2102 (S15, 8008). The response notice (B) includes the handle valuegenerated at step S12 and the recv SDP information of the terminal B5 cincluded in the 200 OK received at step S13, for example. The SPCCmodule part 2102 stores the handle value and the recv SDP informationincluded in the received response notice (B) in the terminal informationtable 2030, associated with the terminal B5 c. The handle value may bestored at an appropriate timing from step S12 to step S14. The 3PCCmodule part 2102 updates the terminal state 2033 corresponding to theterminal B5 c of the terminal information table 2030 to “Call Complete(session established state)”. Also, the 3PCC module part 2102 updatesthe call state 2022 corresponding to the terminal B5 c of the callparticipant information table 2020 to “Call Participant Connected(connected state)”. Also, the 3PCC module part 2102 updates the sessionstate of the session information table 2010 to “Connected (connectedstate)”.

The 3PCC module part 2102 sends the session ID, and the IP address andport number of the terminal B5 c included in the received recv SDPinformation to the media stream control part 2103. The media streamcontrol part 2103 stores, associated with the received session ID, theIP address and port number of the terminal B5 c in the partner IPaddress (2) 2046 and the partner port number (2) 2047 of the mediastream control information table 2040.

The 3PCC module part 2102 sends a pseudo RBT stop request to the mediastream control part 2103 (S102, 8009). The media stream control part2103 stops sending the pseudo RBT in accordance with the pseudo RBT stoprequest.

The SOAP-SIP adapter 2 starts to transfer the media stream between theterminal A5 b and the terminal B5 c (8010).

For example, the terminal A5 b sends the media stream to the SOAP-SIPadapter 2 in accordance with the RTP (S16). At this time, the terminalA5 b sets the IP address and port number of the SOAP-SIP adapter 2stored at step S6 to the destination, and sets its own IP address andport number to the sender.

The media stream control part 2103 of the SOAP-SIP adapter 2 transfersthe received media stream to the terminal B5 c by referring to the mediastream control information table 2040 (S17). For example, the mediastream control part 2103 acquires the corresponding partner IP addressand port number by referring to the media stream control informationtable 2040 based on the sender IP address and port number of thereceived media stream. In an example of the media stream controlinformation table 2040 as shown in FIG. 3D, the sender IP address andport number of the received media stream are the IP address (10.0.2.1)and port number (20000) of the terminal A5 b, and the correspondingpartner IP address (2) 2046 (10.0.2.2) and port number (2) 2047 (30000)are acquired. The media stream control part 2103 transfers the receivedmedia stream to the terminal B5 c in accordance with the acquired IPaddress and port number.

Similarly, the terminal B5 c sends the media stream to the SOAP-SIPadapter 2 in accordance with the RTP (S18). In the same manner as thecase of the terminal A5 b, the terminal B5 c sets the IP address andport number of the SOAP-SIP adapter 2 stored at step S12 to thedestination, and sets its own IP address and port number to the sender.

The media stream control part 2103 of the SOAP-SIP adapter 2 transfersthe received media stream to the terminal A5 b by referring to the mediastream control information table 2040 (S19). In an example of the mediastream control information table 2040 as shown in FIG. 3D, the sender IPaddress and port number of the received media stream are the IP address(10.0.2.2) and port number (30000) of the terminal B5 c, and thecorresponding partner IP address (1) 2044 (10.0.2.1) and port number (1)2045 (20000) are acquired. The media stream control part 2103 transfersthe received data stream to the terminal A5 b in accordance with theacquired IP address and port number.

As described above, the IP address establishing the signaling channeland the IP address establishing the data channel become the same,whereby the data from the terminal A5 b is received by the SOAP-SIPadapter 2 and transferred to the terminal B5 c, and the data from theterminal B5 c is received by the SOAP-SIP adapter 2 and transferred tothe terminal A5 b, so that the 3PCC service on the NGN with the assuredcommunication quality is enabled.

FIG. 13 is a sequence chart (2) for explaining the 3PCC serviceprocedure according to the first embodiment. FIG. 9 is a flowchart forexplaining the operation in receiving a call information (sessioninformation) request in the SOAP-SIP adapter 2 according to the firstembodiment.

Referring to FIGS. 13 and 9, the operation that the Web server 1acquires the call information will be described below. Herein, the Webserver 1 can acquire the information corresponding to the designatedsession ID. The processings of steps S21 to S24 in FIG. 13 correspond tothe processings of steps S16 to S19 as described above.

The Web server 1 sends an SOAP get Call Session Information Request(session information request, call information request) to the SOAP-SIPadapter 2 (S25). The SOAP get Call Session Information Request includesthe session ID of the call information to be acquired. Morespecifically, the Web sever 1 generates the SOAP get Call SessionInformation Request including the session ID stored at step S4 asdescribed above, and sends it to the SOAP-SIP adapter 2. The Web server1 may select the session ID of the call information to be acquired fromthe session ID stored at step S4 as described above, based on the useroperation from the terminal 5 a.

The SOAP-SIP adapter 2 searches the session information table 2010 heldin the SOAP-SIP adapter 2 with the session ID included in the SOAP getCall Session Information Request as the key, and sends the SOAP get CallSession Information Response including the table information of thematched session ID 2011 (S26 to S28). The detailed operation of stepsS26 to S28 in the SOAP-SIP adapter 2 will be described below.

First of all, the SOAP control part 2101 of the SOAP-SIP adapter 2receives the SOAP get Call Session Information Request, and sends asession information request to the 3PCC module part 2102 (S26). Thissession information request includes the session ID in the SOAP get CallSession Information Request.

The SPCC module part 2102 receives the session information request(9001), and searches the session information table 2010 for the sessionID 2011 based on the session ID included in the received sessioninformation request (9002). If the session ID included in the receivedsession information request is already registered in the sessioninformation table 2010, the session information corresponding to thepertinent session ID 2011 is specified (9003). The 3PCC module part 2102acquires the URI 2021 and the call state 2022 corresponding to eachterminal 5 b, 5 c, for example, by referring to the call participantinformation table (call participant state) 2020 corresponding to thepertinent session ID 2011 (9004). Further, the 3PCC module part 2102acquires the recv SDP information 2036 of each terminal from theterminal information (for Client A) 2030_A and the terminal information(for Client B) 2030_B corresponding to the pertinent session ID 2011,for example.

The 3PCC module part 2102 generates a session information requestsuccess response including the session ID 2011, the acquired URI 2021,the call state 2022 and the recv SDP information 2036 (9005), and sendsthe generated session information request success response to the SOAPcontrol part 2101 (S27). The SOAP control part 2101 receives the sessioninformation request success response, and sends an SOAP get Call SessionInformation Response (session information request success response) tothe Web server 1 (S28, 9006). The SOAP get Call Session InformationResponse includes the session ID, the URI, the call state and the recvSDP information in the received session information request successresponse and is generates in accordance with the SOAP.

If the session ID included in the received session information requestis not registered at step 9002, the 3PCC module part 2102 generates asession information request failure response (error response message)(9007), and sends the generated session information request failureresponse to the SOAP control part 2101. The SOAP control part 2101receives the session information request failure response, and sends theSOAP get Call Session Information Response indicating the sessioninformation request failure to the Web server 1 (9006).

The Web server 1 receives the SOAP get Call Session InformationResponse, and can confirm the session state as to whether or not therequested communication comes into existence by referring to the callstate included in the received SOAP get Call Session InformationResponse, for example. For example, if the call is terminated from theterminal, the call state becomes “Call Participant Terminated(terminated state)”, whereby the Web server 1 can judge that the call isterminated from the terminal A5 b or terminal B5 c. Also, for example,if the call state is not normal, the Web server 1 may stop thecommunication using an SOAP end Call Session Request as will bedescribed later.

FIG. 14 is a sequence chart (3) for explaining the 3PCC serviceprocedure according to the first embodiment. FIG. 10 is a flowchart forexplaining the operation in receiving a call participant informationrequest in the SOAP-SIP adapter 2 according to the first embodiment.

Referring to FIGS. 14 and 10, the operation that the Web server 1acquires the call participant information will be described below.Herein, the Web server 1 can acquire the user information correspondingto the designated SIP-URI. The processings of steps 931 to S34 in FIG.14 correspond to the processings of steps S16 to S19 as described above.

The Web server 1 sends an SOAP get Call Participants Information Request(call participant information request) to the SOAP-SIP adapter 2 (S35).The SOAP get Call Participants Information Request includes the sessionID and URI of the call participant information to be acquired. Morespecifically, the Web sever 1 generates the SOAP get Call SessionInformation Request including the session ID stored at step S4 asdescribed above and the SIP-URI of the desired call participant, andsends it to the SOAP-SIP adapter 2. As one example, the Web server 1 mayselect the session ID and the user identifier (e.g., user namecorresponding to the terminal A5 b, terminal B5 c) of the callinformation to be acquired based on the user operation from the terminal5 a. The Web server 1 can acquire the SIP-URI corresponding to the inputuser identifier, because the user identifier and the SIP-URI of the userare associated and prestored as above described.

The SOAP-SIP adapter 2 searches the session information table 2010 heldin the SOAP-SIP adapter 2 with the session ID included in the SOAP getCall Participants Information Request as the key, and specifies thetable information of the matched session ID 2011. Further, the SOAP-SIPadapter 2 searches the call participant information table 2020 with theSIP-URI included in the SOAP get Call Participants Information Requestas the key, and sends the SOAP get Call Participants InformationResponse including the table information corresponding to the matchedSIP-URI 2021 (S36 to S38). The operation of steps S36 to S38 in theSOAP-SIP adapter 2 will be described below.

The SOAP control part 2101 of the SOAP-SIP adapter 2 receives the SOAPget Call Participants Information Request, and sends a call participantinformation request to the 3PCC module part 2102 (S36). This callparticipant information request includes the session ID and the SIP-URIin the SOAP get Call Participants Information Request. The 3PCC modulepart 2102 receives the call participant information request (1001), andsearches the session information table 2010 for the session ID 2011,based on the session ID included in the received call participantinformation request (1002). If the session ID included in the receivedcall participant information request is already registered in thesession information table 2010, the session information is specified bythe pertinent session ID 2011 (1003). The 3PCC module part 2102 searchesthe call participant information table (call participant state) 2020corresponding to the pertinent session ID 2011 for the URI 2021, basedon the SIP-URI included in the received call participant informationrequest (1004). If the SIP-URI included in the received call participantinformation request is already registered, the 3PCC module part 2102acquires the call state 2022 corresponding to the pertinent URI 2021(1005). Also, the 3PCC module part 2102 acquires the corresponding recvSDP information 2036 by referring to the To URI 2038 of the terminalinformation table 2030, based on the SIP-URI included in the receivedcall participant information request.

The 3PCC module part 2102 generates a call participant informationrequest success response including the URI 2021, the acquired call state2022 and the recv SDP information 2036 (1006), and sends the generatedcall participant information request success response to the SOAPcontrol part 2101 (S37). The SOAP control part 2101 receives the callparticipant information request success response, and sends an SOAP getCall Participants Information Response (call participant informationrequest success response) to the Web server 1 (S38, 1007). The SOAP getCall Participants Information Response includes the URI, the call stateand the recv SDP information in the received call participantinformation request success response and is generated in accordance withthe SOAP.

If the session ID included in the received call participant informationrequest is not registered at step 1002, and the SIP-URI included in thereceived call participant information request is not registered at step1004, the 3PCC module part 2102 generates a call participant informationrequest failure response (error response message) (1008), and sends thegenerated call participant information request failure response to theSOAP control part 2101. The SOAP control part 2101 receives the callparticipant information request failure response, and sends the SOAP getCall Participants Information Response indicating the call participantinformation request failure to the Web server 1 (1007).

FIG. 15 is a sequence chart (4) for explaining the 3PCC serviceprocedure according to the first embodiment. FIG. 11 is a flowchart forexplaining the operation in receiving a call end request in the SOAP-SIPadapter 2 according to the first embodiment.

Referring to FIGS. 15 and 11, the operation that the Web server 1 endsthe call will be described below. The processings of steps S41 to S44 inFIG. 15 correspond to the processings of steps S16 to S19 as describedabove.

The Web server 1 sends an SOAP end Call Session Request (call endrequest) to the SOAP-SIP adapter 2 (S45). The SOAP end Call SessionRequest includes the session ID of the call to be ended. Morespecifically, the Web sever 1 generates the SOAP end Call SessionRequest including the session ID stored at step S4 as described above,and sends it to the SOAP-SIP adapter 2. As one example, the Web server 1may select the session ID of the call to be ended from the session IDstored at step S4 as described above, based on the user operation fromthe terminal 5 a.

The SOAP-SIP adapter 2 searches the session information table 2010 heldin the SOAP-SIP adapter 2 with the session ID included in the SOAP endCall Session Request as the key, specifies the terminals 5 b, 5 c to bedisconnected from the table information of the matched session ID 2011and disconnects them (S46 to S56). The detailed operation of steps S46to S56 in the SOAP-SIP adapter 2 will be described below.

The SOAP control part 2101 of the SOAP-SIP adapter 2 receives the SOAPend Call Session Request (call end request), and sends the call endrequest to the 3PCC module part 2102 (S46). This call end requestincludes the session ID in the SOAP end Call Session Request. The 3PCCmodule part 2102 receives the call end request (1101), and searches thesession information table 2010 for the session ID 2011, based on thesession ID included in the received call end request (1102).

If the session ID included in the received call end request is alreadyregistered in the session information table 2010, the 3PCC module part2102 generates a call end request success response (1109), and sends thegenerated call end request success response to the SOAP control part2101 (S47). The SOAP control part 2101 receives the call end requestsuccess response, and sends an SOAP end Call Session Response (call endrequest success response) to the Web server 1 (S48, 1110). For the Soapend Call Session Response, only the success response may be sent.

Also, the session information is specified by the pertinent session ID2011 to specify the two parties (here the terminal A5 b, terminal B5 c)during the telephone communication (1103). For example, the 3PCC modulepart 2102 acquires the SIP-URI 2021 of each terminal A5 b, terminal B5 cby referring to the call participant information table 2020corresponding to the session ID included in the received call endrequest. The media stream control part 2103 stops the transfer of mediastream (1104). A media stream transfer stop request may be sent from the3PCC module part 2102 to the media stream control part 2103.

The 3PCC module part 2102 sends a disconnect request (A) including theacquired SIP-URI to the SIP control part 2104 in accordance with one ofthe acquired SIP-URIs (549, 1105). The SIP control part 2104 receivesthe disconnect request (A), and sends a BYE message (A) of the SIP tothe terminal A5 b with the SIP-URI included in the received disconnectrequest (A) as the To URI (S50).

Likewise, the 3PCC module part 2102 sends a disconnect request (B)including the acquired SIP-URI to the SIP control part 2104 inaccordance with the other acquired SIP-URI (551, 1106). The SIP controlpart 2104 receives the disconnect request (B), and sends a BYE message(B) to the terminal B5 c with the SIP-URI included in the receiveddisconnect request (B) as the To URI (S52).

The terminal A5 b sends a 200 OK (A) for the BYE message (A) received atstep S50 to the SOAP-SIP adapter 2 (S53). The SIP control part 2104 ofthe SOAP-SIP adapter 2 receives the 200 OK (A), and sends a disconnectcomplete notice (A) to the 3PCC module part 2102 (554, 1107).

Likewise, the terminal B5 c sends a 200 OK (B) for the BYE message (B)received at step S52 to the SOAP-SIP adapter 2 (S55). The SIP controlpart 2104 of the SOAP-SIP adapter 2 receives the 200 OK (B), and sends adisconnect complete notice (B) to the 3PCC module part 2102 (S56, 1108).

If the session ID included in the received call end request is notregistered at step 1102, the 3PCC module part 2102 generates a call endrequest failure response (error response message) (1111), and sends thegenerated call end request failure response to the SOAP control part2101. The SOAP control part 2101 receives the call end request failureresponse, and sends the SOAP end Call Session Response indicating thecall end request failure to the Web server 1 (1110).

2. Second Embodiment Network Configuration

FIG. 4 is an explanatory view showing a configuration example of acommunication network according to a second embodiment.

The communication network (system) of this embodiment comprises a SIPserver 3 and an SOAP-SIP adapter 6 a, 6 b, for example. The SIP server 3is installed in an NGN N2.

The SOAP-SIP adapter 6 a communicates via the NGN N2 with the SOAP-SIPadapter 6 b. Also, a terminal 7 a and a terminal 7 b communicate via theSOAP-SIP adapter 6 a and the SOAP-SIP adapter 6 b. It is predeterminedwhich SOAP-SIP adapter 6 the terminal 7 is connected to, in which theSOAP-SIP adapter 6 a and the terminal A7 a correspond one to one, andthe SOAP-SIP adapter 6 b and the terminal B7 b also correspond one toone. For example, to communicate with the terminal B7 b, it is possibleto communicate with the terminal B7 b if the SOAP-SIP adapter 6 b isdesignated. Also, the SOAP-SIP adapter 6 and the terminal 7 maycorrespond one to many, and the correspondence between the SOAP-SIPadapter 6 and the terminal 7 to be connected may be stored in anappropriate device.

FIG. 5 is an explanatory view showing a configuration example of theSOAP-SIP adapter 6 according to the second embodiment.

The SOAP-SIP adapter 6 of this embodiment comprises an NGN connectionmodule part 5102, instead of the 3PCC module part 2102 of the firstembodiment, for example. The NGN connection module part 5102 has aconnection information table 5010, which has a terminal informationtable 5020. A CPU 5001, an IF 5003 a, 5003 b, an SOAP control part 5101,a media stream control part 5103, and a SIP control part 5104 are thesame as those of the first embodiment.

FIG. 6A is an explanatory view showing one example of the organizationof the connection information table 5010 in the SOAP-SIP adapter 6 aaccording to the second embodiment.

The connection information table 5010 stores, associated with aconnection ID 5011, a connection state 5012 and the terminal information5013, for example.

The connection ID 5011 is the information identifying the connectioncorresponding to the connection request from the terminal 7. Forexample, the connection in the Transmission Control Protocol (TCP) isidentified. The connection ID 5011 is generated for each SOAP-SIPadapter 6. The connection state 5012 indicates the state of connection,corresponds to the session state 2012 of the first embodiment, forexample, and stores the same state. The terminal information 5013corresponds to the terminal information table 5020.

FIG. 6B is an explanatory view showing one example of the organizationof the terminal information table 5020 in the SOAP-SIP adapter 6 aaccording to the second embodiment.

The terminal information table 5020 stores a handle value 5021, aconnection ID 5022, a terminal state 5023, the send SDP information5024, the recv SDP information 5025, a From URI 5026 and a To URI 5027,for example.

The handle value 5021 is the information identifying the session of SIPbetween the SOAP-SIP adapter 6 a and the SOAP-SIP adapter 6 b. Theconnection ID 5022 corresponds to the connection ID 5011 in theconnection information table 5010 as described above. The terminal state5023 indicates the state of session between the SOAP-SIP adapter 6 a andthe SOAP-SIP adapter 6 b. The terminal state 5023 is stored in the samestate as the terminal state 2033 of the first embodiment, for example.The send SDP information 5024 includes the IP address and the portnumber of the SOAP-SIP adapter 6 itself, for example. In an example ofthe SOAP-SIP adapter 6 a as shown in FIG. 6B, it includes the IP address(10.0.1.1) and the port number (10000) of the SOAP-SIP adapter 6 a. Therecv SDP information 5025 includes the IP address and the port number ofthe SOAP-SIP adapter 6 to be connected, for example. In the example ofFIG. 6B, it includes the IP address (10.0.2.1) and the port number(20000) of the SOAP-SIP adapter 6 b. The From URI 5026 indicates theSIP-URI of the SOAP-SIP adapter 6 itself, for example. In the example ofFIG. 6B, it indicates the SIP-URI of the SOAP-SIP adapter 6 a. The ToURI 5027 indicates the SIP-URI of the SOAP-SIP adapter 6 to beconnected, for example. In the example of FIG. 6B, it indicates theSIP-URI of the SOAP-SIP adapter 6 b.

FIG. 6C is an explanatory view showing one example of the organizationof the media stream control information table 5030 in the SOAP-SIPadapter 6 a according to the second embodiment.

The media stream control information table 5030 of this embodimentstores a connection ID 5031, instead of the session ID 2041 of the firstembodiment, for example.

The connection ID 5031 corresponds to the connection ID 5011 of theconnection information table 5010. The other items, including a mediastream sending/receiving IP address 5032, a media streamsending/receiving port number 5033, a partner IP address (1) 5034, apartner port number (1) 5035, a partner IP address (2) 5036, and apartner port number (2) 5037 are the same as those of the firstembodiment. In the SOAP-SIP adapter 6 a of this embodiment, the partnerIP address (1) 5034 and the partner port number (1) 5035 store the IPaddress and the port number of the SOAP-SIP adapter 6 b, and the partnerIP address (2) 5036 and the partner port number (2) 5037 store the IPaddress and the port number of the terminal A7 a. Also, the media streamsending/receiving IP address 5032 and the media stream sending/receivingport number 5033 store the IP address and the port number of theSOAP-SIP adapter 6 a as in the first embodiment.

FIG. 21A is an explanatory view showing one example of the organizationof a connection information table 6010 in the SOAP-SIP adapter 6 baccording to the second embodiment. FIG. 21B is an explanatory viewshowing one example of the organization of a terminal information table6020 in the SOAP-SIP adapter 6 b according to the second embodiment.FIG. 21C is an explanatory view showing one example of the organizationof a media stream control information table 6030 in the SOAP-SIP adapter6 b according to the second embodiment.

The organization of each table 6010, 6020, 6030 in the SOAP-SIP adapter6 b is the same as that of each table 5010, 5020, 5030 in the SOAP-SIPadapter 6 a as described above.

In the terminal information table 6020 of the SOAP-SIP adapter 6 b, theIP address and the port number of the SOAP-SIP adapter 6 b are stored inthe send SDP information 6024, and the IP address and the port number ofthe SOAP-SIP adapter 6 a to be connected is stored in the recv SDPinformation 6025. Also, a From URI 6026 indicates the SIP-URI of theSOAP-SIP adapter 6 b and a To URI 6027 indicates the SIP-URI of theSOAP-SIP adapter 6 a.

Also, in the media stream control information table 6030, a partner IPaddress (1) 6034 and a partner port number (1) 6035 store the IP addressand the port number of the SOAP-SIP adapter 6 a, and a partner IPaddress (2) 6036 and a partner port number (2) 6037 store the IP addressand the port number of the terminal B7 b. A media streamsending/receiving IP address 6032 and a media stream sending/receivingport number 6033 store the IP address and the port number of theSOAP-SIP adapter 6 b.

(Operation)

FIG. 19 is a sequence chart (1) for explaining an NGN connection serviceprocedure according to the second embodiment. FIG. 16 is a flowchart forexplaining the operation in receiving a connection start request in theSOAP-SIP adapter 6 according to the second embodiment. FIG. 22 is aflowchart for explaining the operation in receiving a call incomingnotice in the SOAP-SIP adapter 6 according to the second embodiment.FIG. 17 is a flowchart for explaining the operation in receiving aconnection information request in the SOAP-SIP adapter 6 according tothe second embodiment.

In this embodiment, it is possible to provide a service for connectingthe self terminal and the other partner terminal on the NGN with theassured communication quality without being aware of the protocol of theSIP.

Most of the existent application terminals mount no SIP for reservingthe communication band on the NGN, and have a problem that thecommunication on the NGN is impossible. In this embodiment, it ispossible to reserve the communication band with the partner terminal B7b without being aware of the SIP by sending a connection start requestSOAP message to the SOAP-SIP adapter 6 with a trigger of selecting thepartner to be communicated on the screen of the terminal Ala, as oneexample. After reserving the communication band, the terminal 7 can makethe communication on the reserved band through the already existentoperation that is indifferent from the internet.

The operation that the terminal 7 starts the connection will bedescribed below.

The terminal A7 a connected to the SOAP-SIP adapter 6 a opens (breaks) aqueue port for the SOAP-SIP adapter 6 a at the start up, for example.Thereby, sending and receiving the data between the terminal A7 a andthe SOAP-SIP adapter 6 a is enabled. At this time, the SOAP-SIP adapter6 a receives the IP address and port number of the terminal A7 a, andstores the received IP address and port number of the terminal A7 a inthe appropriate storage part. The terminal B7 b and the SOAP-SIP adapter6 b have also the same configuration. The terminal 7 is not limited tothe above example, but may open the queue port at an appropriate timing.The terminal A7 a sends an SOAP connect Request (connection request) tothe SOAP-SIP adapter 6 a (S61). The SOAP connect Request includes theSIP-URI of the SOAP-SIP adapter 6 b corresponding to the terminal B7 bto be connected. For example, the terminal A7 a may select the useridentifier of the user or the SIP-URI of the SOAP-SIP adapter 6 to beconnected from the appropriate input part, based on the user operation.In selecting the user identifier, for example, the terminal A7 a mayspecify the SIP-URI of the SOAP-SIP adapter 6 corresponding to the inputuser identifier, because the user identifier and the SIP-URI of theSOAP-SIP adapter 6 to which the terminal 7 of the user is connected areassociated and prestored. Also, a Web server in which the useridentifier and the SIP-URI of the SOAP-SIP adapter 6 to which the userterminal 7 is connected are associated and prestored may be installed,and the Web server may return the SIP-URI of the SOAP-SIP adapter 6corresponding to the user identifier selected at the terminal A7 a.

The SOAP control part 5101 a of the SOAP-SIP adapter 6 a receives theSOAP connect Request, and sends a connection request (B) to the NGNconnection module part 5102 a of the SOAP-SIP adapter 6 a (S62). Thisconnection request (B) includes the SIP-URI in the SOAP connect Request.The SOAP-SIP adapter 6 a starts the connection to this SIP-URI.

More specifically, first of all, the NGN connection module part 5102 areceives the connection request (B) (1601), and generates the connectionID (1602). The generation of the connection ID is the same as in FIG. 7and its description of the first embodiment. Referring to FIGS. 6A and6B, this embodiment will be described below, although the explanation ispartially duplicated with that of FIG. 7. The NGN connection module part5102 a stores the generated connection ID in the connection informationtable 5010 and the terminal information table 5020. The NGN connectionmodule part 5102 a sets the connection state 5012 of the connectioninformation table 5010 to “Initial (initial state)”. Further, the NGNconnection module part 5102 a stores the SIP-URI included in thereceived connection request (B) in the To URI 5027 of the terminalinformation table 5020.

Also, the NGN connection module part 5102 a sets the terminal state 5023of the terminal information table 5020 to “Initial (initial state)”. TheNGN connection module part 5102 a stores the send SDP information 5024including the IP address and the port number of the SOAP-SIP adapter 6 ain the terminal information table 5020. Also, the NGN connection modulepart 5102 a stores the SIP-URI of the SOAP-SIP adapter 6 a in the FromURI 5026 of the terminal information table 5020. The SIP-URI, the IPaddress and the port number of the SOAP-SIP adapter 6 a are prestored inthe appropriate storage part.

The NGN connection module part 5102 a generates a connection successresponse (B) (1607), and sends the generated connection success response(B) to the SOAP control part 5101 a (S63). The connection successresponse (B) includes the generated connection ID. The SOAP control part5101 a receives the connection success response (B), and sends an SOAPconnect Response (connection success response) to the terminal A7 a(S64, 1608). The SOAP connect Response includes the connection ID in thereceived connection success response (B), and is generated in accordancewith the SOAP. The terminal A7 a receives the SOAP connect Response, andstores the connection ID included in the received SOAP connect Responsein the appropriate storage part.

If the generation of the connection ID fails at step 1602, the NGNconnection module part 5102 a generates a connection request failureresponse (error response message) (1609), and sends it to the SOAPcontrol part 5101 a. The SOAP control part 5101 a receives theconnection request failure response, and sends the SOAP connect Responseindicating the connection request failure to the terminal A7 a (1608).

Next, the SOAP-SIP adapter 6 a establishes the session with the SOAP-SIPadapter 6 b.

First of all, the NGN connection module part 5102 a acquires a mediastream control transfer port (1603). The NGN connection module part 5102a sends a call outgoing request (B) to the SIP control part 5104 a ofthe SOAP-SIP adapter 6 a (S65, 1604). The call outgoing request (B)includes the send SDP information 5024, the From URI 5026 and the To URI5027 stored in the terminal information table 5020.

The SIP control part 5104 a receives the call outgoing request (B), andsends an INVITE message (B) of the SIP to the SOAP-SIP adapter 6 b inaccordance with the To URI included in the received call outgoingrequest (B) (S66). The INVITE message (B) includes at least the send SDPinformation, the From URI, and the To URI in the received call outgoingrequest (B), for example. Also, the SIP control part 5104 a generatesthe handle value identifying the session of the SIP with the SOAP-SIPadapter 6 b.

The operation of each part in the SOAP-SIP adapter 6 b will be describedbelow.

The SIP control part 5104 b of the SOAP-SIP adapter 6 b receives theINVITE message (B), and sends a call incoming notice (A) to the NGNconnection module part 5102 b of the SOAP-SIP adapter 6 b (S67). Thecall incoming notice (A) includes the send SDP information, the From URIand the To URI in the received INVITE message (B).

The NGN connection module part 5102 b receives the call incoming notice(A) (1901), and generates the connection ID (1902). In this embodiment,the connection ID is generated independently in the SOAP-SIP adapter 6 aand the SOAP-SIP adapter 6 b. The generation of the connection ID is thesame as at step 1602 as described above. The NGN connection module part5102 b stores the generated connection ID in the connection informationtable 6010 and the terminal information table 6020. The NGN connectionmodule part 5102 b sets the connection state 6012 of the connectioninformation table 6010. For example, it sets the connection state 6012to “Initial (initial state)” or “Connected (connected state)”. The“Initial” or “Connected” may be changed at an appropriate timing.Moreover, the NGN connection module part 5102 b stores the send SDPinformation included in the received call incoming notice (A) in therecv SDP information 6025 of the terminal information table 6020. TheNGN connection module part 5102 b stores the From URI included in thereceived call incoming notice (A) in the To URI 6027 of the terminalinformation table 6020, and similarly stores the To URI (i.e., its ownSIP-URI) included in the received call incoming notice (A) in the FromURI 6026.

Also, the NGN connection module part 5102 b sets the terminal state 6023of the terminal information table 6020. For example, it appropriatelysets the terminal state 6023 to “Initial (initial state)” or “CallComplete (session established state)”. The terminal state 6023 may beappropriately changed. The NGN connection module part 5102 b stores theIP address and the port number of the SOAP-SIP adapter 6 b in the sendSDP information 6024 of the terminal information table 6020. The IPaddress and the port number of the SOAP-SIP adapter 6 b are prestored inthe appropriate storage part. Also, the SIP control part 5104 bgenerates the handle value identifying the session of the SIP with theSOAP-SIP adapter 6 a and stores it in the terminal information table6020.

The NGN connection module part 5102 b of the SOAP-SIP adapter 6 bacquires the media stream control transfer port (1903). The NGNconnection module part 5102 b sends the generated connection ID, the IPaddress and port number of the SOAP-SIP adapter 6 a included in the sendSDP information in the received call incoming notice (A), and the IPaddress and port number of the terminal B7 b stored by port open to themedia stream control part 5103 b. The media stream control part 5103 bstores each received information in the media stream control informationtable 6030. For example, the media stream control part 5103 b stores thereceived IP address and port number of the SOAP-SIP adapter 6 a in thepartner IP address (1) 6034 and the partner port number (1) 6035, andstores the received IP address and port number of the terminal B7 b inthe partner IP address (2) 6036 and the partner port number (2) 6037.Also, the media stream control part 5103 b stores the receivedconnection ID, and stores its own IP address and port number in themedia stream sending/receiving IP address 6032 and the media streamsending/receiving port number 6033. Thereby, the SOAP-SIP adapter 6 bcan start the transfer of media stream (1904).

The NGN connection module part 5102 b generates a response (A), andsends it to the SIP control part 5104 b (S68, 1905). The response (A)includes the send SDP information 6024, the From URI 6026 and the To URI6027 stored in the terminal information table 6020. The SIP control part5104 b receives the response (A), and sends a 200 OK (B) of the SIP tothe SOAP-SIP adapter 6 a (S69). The 200 OK (B) includes at least thesend SDP information, the From URI and the To URI in the receivedresponse (A), for example.

If the generation of the connection ID fails at step 1902 as describedabove, the NGN connection module part 5102 b disconnects the session ofSIP with the SOAP-SIP adapter corresponding to the terminal A7 a (1906).

Returning to the description of the SOAP-SIP adapter 6 a, the SIPcontrol part 5104 a of the SOAP-SIP adapter 6 a receives the 200 OK (B)and sends an ACK (B) of the SIP to the SOAP-SIP adapter 6 b (S70). TheSIP control part 5104 a sends a response notice (B) to the NGNconnection module part 5102 a (S71, 1605). The response notice (B)includes the handle value generated at step S66 and the send SDPinformation included in the 200 OK (B) received at step S69. The NGNconnection module part 5102 a stores the handle value included in thereceived response notice (B) in the terminal information table 5020.Also, the NGN connection module part 5102 a stores the send SDPinformation included in the received response notice (B) in the recv SDPinformation 5025 of the terminal information table 5020. The handlevalue may be stored at an appropriate timing. The NGN connection modulepart 5102 a updates the terminal state 5023 of the terminal informationtable 5020 to “Call Complete (session established state)”. Also, the NGNconnection module part 5102 a updates the connection state 5012 of theconnection information table 5010 to “Connected (connected state)”. Theterminal state 2023 may be updated appropriately in sending or receivingthe SIP message (e.g., 200 OK and so on).

The NGN connection module part 5102 a sends the generated connection ID,the IP address and port number of the terminal A7 a stored by port open,the IP address and port number of the SOAP-SIP adapter 6 b included inthe received send SDP information to the media stream control part 5103a. The media stream control part 5103 a stores each received informationin the media stream control information table 5030. For example, themedia stream control part 5103 a stores the received IP address and portnumber of the SOAP-SIP adapter 6 b in the partner IP address (1) 5034and the partner port number (1) 5035, and stores the received IP addressand port number of the terminal A7 a in the partner IP address (2) 5036and the partner port number (2) 5037. Also, the media stream controlpart 5103 a stores the received connection ID, and stores its own IPaddress and port number in the media stream sending/receiving IP address5032 and the media stream sending/receiving port number 5033. Thereby,the SOAP-SIP adapter 6 a can start the transfer of media stream (1606).

Next, the operation that the terminal 7 acquires the connectioninformation will be described below.

The terminal A7 a sends an SOAP get Connection Information List Request(connection information request) to the SOAP-SIP adapter 6 a (S72). TheSOAP get Connection Information List Request includes the connection IDof the connect information (connection information) to be acquired. Morespecifically, the terminal A7 a generates the SOAP get ConnectionInformation List Request including the connection ID stored at step S64as described above. As one example, the terminal A7 a periodicallyperforms the processing at step S72 after receiving the SOAP connectionResponse at step S64.

The SOAP-SIP adapter 6 a searches the connection information table 5010held in the SOAP-SIP adapter 6 a with the connection ID included in theSOAP get Connection Information List Request as the key, and sends anSOAP get Connection Information List Response including the tableinformation of the matched connection ID 5011 (S73 to S75). The detailedoperation of steps S73 to S75 in the SOAP-SIP adapter 6 a will bedescribed below.

First of all, the SOAP control part 5101 a of the SOAP-SIP adapter 6 areceives the SOAP get Connection Information List Request, and sends aconnection information request to the NGN connection module part 5102 a(S73). This connection information request includes the connection ID inthe SOAP get Connection Information List Request.

The NGN connection module part 5102 a receives the connectioninformation request (1701), and searches the connection informationtable 5010 for the connection ID 5011, based on the connection IDincluded in the received connection information request (1702). If theconnection ID included in the received connection information request isalready registered in the connection information table 5010, theconnection information corresponding to the pertinent connection ID 5011is specified (1703). The NGN connection module part 5102 a acquires theconnection state 5012 corresponding to the pertinent connection ID 5011(1704). The NGN connection module part 5102 a is not limited to theconnection state 5012, but may further acquire appropriate informationstored in the connection information table 5010 and the terminalinformation table 5020.

The NGN connection module part 5102 a generates a connection informationsuccess response including the acquired connection state 5012 (1705),and sends the generated connection information success response to theSOAP control part 5101 a (S74). The SOAP control part 5101 a receivesthe connection information success response, and sends an SOAP getConnection Information List Response to the terminal A7 a (S75, 1706).The SOAP get Connection Information List Response includes theconnection state in the received connection information successresponse, and is generated in accordance with the SOAP.

If the connection ID included in the received connection informationrequest is not registered in the connection information table 5010 atstep 1702, the NGN connection module part 5102 a generates a connectioninformation failure response (error response message) (1707), and sendsthe generated connection information failure response to the SOAPcontrol part 5101 a. The SOAP control part 5101 a receives theconnection information failure response, and sends the SOAP getConnection Information List Response indicating the connectioninformation request failure to the terminal A7 a (1706).

The terminal A7 a receives the SOAP get Connection Information ListResponse, and can confirm the state of connection by referring to theconnection state included in the received SOAP get ConnectionInformation List Response. Thereby, if it is confirmed that theconnection state is “Connected (connected state)”, for example, terminalA7 a and the terminal B7 b start the signaling at the AP level inaccordance with the HTTP (S76 to S81), and communicate the media streamin accordance with the RTP (S82 to S87).

The transfer of signal and media stream will be described below inconnection with the media stream from the terminal A7 a to the terminalB7 b, for example. The terminal A7 a sends the media stream from thesender with its own IP address and port number set to the destinationwith the IP address and port number of the SOAP-SIP adapter 6 a set(S82). The IP address and the port number of the SOAP-SIP adapter 6 aare prestored in the appropriate storage part.

The media stream control part 5103 a of the SOAP-SIP adapter 6 atransfers the received media stream to the SOAP-SIP adapter 6 b byreferring to the media stream control information table 5030 (S83). Thetransfer operation is the same as in the first embodiment. Referring toFIG. 6C, the SOAP-SIP adapter 6 a of this embodiment will be describedbelow. The sender IP address and port number of the received mediastream are the IP address (192.168.10.1) and port number (30000) of theterminal A7 a, whereby the corresponding partner IP address (1) 5034(10.0.2.1) and port number (1) 5035 (20000) are acquired. The NGNconnection module part 5102 a transfers the received media stream to theSOAP-SIP adapter 6 b in accordance with the acquired IP address and portnumber. Also, at this time, the NGN connection module part 5102 a setsthe media stream sending/receiving IP address 5032 and the media streamsending/receiving port number 5033 of the media stream controlinformation table 5030 to the sender.

The media stream control part 5103 b of the SOAP-SIP adapter 6 breceives the media stream, and transfers a received signal to theterminal B7 b by referring to the media stream control information table6030 (S84). Referring to FIG. 21C, the SOAP-SIP adapter 6 b of thisembodiment will be described below. The sender IP address and portnumber of the received media stream are the IP address (10.0.1.1) andport number (10000) of the SOAP-SIP adapter 6 a, whereby thecorresponding partner IP address (2) 6036 (192.168.10.2) and port number(2) 6037 (40000) are acquired. The NGN connection module part 5102 btransfers the received media stream to the terminal B7 b in accordancewith the acquired IP address and port number. Also, at this time, theNGN connection module part 5102 b sets the media streamsending/receiving IP address 6032 and the media stream sending/receivingport number 6033 of the media stream control information table 6030 tothe sender.

In the case of sending the media stream from the terminal B7 b to theterminal A7 a (585 to S87), and the case of sending or receiving thesignal at the AP level between the terminal A7 a and the terminal B7 b(S76 to S81), the operation is also made in the same manner.

As described above, it is possible to reserve the communication bandwith the partner terminal B7 b without being aware of the SIP by sendinga connection start request SOAP message to the SOAP-SIP adapter 6 a witha trigger of selecting the partner to be communicated on the screen ofthe terminal A7 a, as one example. After reserving the communicationband, the terminal 7 can make the communication on the NGN N2 with thereserved band through the already existent operation that is indifferentfrom the internet. Also, the IP address establishing the signalingchannel and the IP address establishing the data channel are the same.

FIG. 20 is a sequence chart (2) for explaining an NGN connection serviceprocedure according to the second embodiment. FIG. 18 is a flowchart forexplaining the operation in receiving a connection end request in theSOAP-SIP adapter 6 according to the second embodiment. FIG. 23 is aflowchart for explaining the operation in receiving a disconnect noticein the SOAP-SIP adapter 6 according to the second embodiment.

Referring to FIGS. 20, 18 and 23, the operation of ending the connectionwill be described below. The processings of steps S91 to S96 in FIG. 20correspond to the processings of steps S82 to S87 as described above.

The terminal A7 a sends an SOAP disconnect Request (disconnect request)to the SOAP-SIP adapter 6 a (S97). The SOAP disconnect Request includesthe connection ID of the call to end the connection. More specifically,the terminal A7 a generates the SOAP disconnect Request including theconnection ID stored at step S64 as described above. As one example, theterminal A7 a may select the connection ID of the call to end theconnection from the connection ID stored at step S64 as described above,based on the user operation from the appropriate input part.

The SOAP-SIP adapter 6 a searches the connection information table 5010held in the SOAP-SIP adapter 6 a with the connection ID as the key,specifies the terminal 7 to be disconnected from the table informationof the matched connection ID 5011, and disconnects it (S98 to S105). Thedetailed operation of steps S98 to S105 in the SOAP-SIP adapter 6 a willbe described below.

First of all, the SOAP control part 5101 a of the SOAP-SIP adapter 6 areceives the SOAP disconnect Request, and sends a disconnect request (B)to the NGN connection module part 5102 a (S98). This disconnect request(B) includes the connection ID in the SOAP disconnect Request.

The NGN connection module part 5102 a receives the disconnect request(1801), and searches the connection information table 5010 for theconnection ID 5011, based on the connection ID included in the receiveddisconnect request (B) (1802). If the connection ID included in thereceived disconnect request (B) is already registered in the connectioninformation table 5010, the NGN connection module part 5102 a generatesa disconnect success response (1807), and sends the generated disconnectsuccess response to the SOAP control part 5101 a (S99). The SOAP controlpart 5101 a receives the disconnect success response, and sends an SOAPdisconnect Response to the terminal Ala (S100, 1808). For the SOAPdisconnect Response, only the success response may be sent.

Also, the media stream control part 5103 a stops the transfer of mediastream (1803). The NGN connection module part 5102 a may send a mediastream transfer stop request to the media stream control part 5103 a.

The NGN connection module part 5102 a generates the disconnect request(B) and sends it to the SIP control part 5104 a (S101, 1804). Morespecifically, the NGN connection module part 5102 a acquires the To URI5027 by referring to the terminal information table 5020 correspondingto the pertinent connection ID 5011. The NGN connection module part 5102a sends the disconnect request (B) including the acquired To URI 5027 tothe SIP control part 5104 a.

The SIP control part 5104 a receives the disconnect request (B), andsends a BYE message (B) of the SIP to the SOAP-SIP adapter 6 b inaccordance with the To URI included in the received disconnect request(B) (S102). The SIP control part 5104 b of the SOAP-SIP adapter 6 breceives the BYE message (B) (2001), and sends a disconnect notice (A)to the NGN connection module part 5102 b (S103). Also, the SIP controlpart 5104 b sends a 200 OK (B) of the SIP to the SOAP-SIP adapter 6 a(S104, 2002).

The media stream control part 5103 b stops the transfer of media stream(2003), and sets the media stream not transferred (2004). The NGNconnection module part 5102 b may send a media stream transfer stoprequest to the media stream control part 5103 b.

The SIP control part 5104 a of the SOAP-SIP adapter 6 a receives the 200OK (B), and sends a disconnect complete notice (B) to the NGN connectionmodule part 5102 a (S105, 1805). The NGN connection module part 5102 areceives the disconnect complete notice (B), and sets the media streamnot transferred (1806).

If the session ID included in the received call end request is notregistered at step 1802, the NGN connection module part 5102 a generatesa call end request failure response (error response message) (1809), andsends the generated call end request failure response to the SOAPcontrol part 5101 a.

The SOAP control part 5101 a receives the call end request failureresponse, and sends the SOAP disconnect Response indicating the call endrequest failure to the terminal Ala (1808).

3. Others Configuration Example in the First Embodiment

According to the first embodiment, a communication system has, forexample, a first server (SOAP-SIP adapter 2), a device (terminal B5 c,Client B) for making an establishment of connection with said firstserver in a SIP protocol, and a first terminal (terminal A5 b, Client A)for communicating with said first server, said first server comprises:

an interface (SOAP control part) for receiving a connection requestmessage (SOAP makeCallSessionRequest);

a processing part (3PCC module part, SIP control part) for making theestablishment of connection with said device in said SIP protocol inaccordance with said received connection request message; and

a first transfer control part (media stream control part) fortransferring data received from said first terminal to said device afterthe establishment of connection by said processing part.

In the communication system described above,

said device is a second terminal (terminal B5 c, Client B),

said communication system further comprises a second server (Web server1) for sending said connection request message for communicating betweensaid first terminal and said second terminal to said first server,

said processing part makes the establishment of connection for saidfirst terminal and said second terminal in said SIP protocol, and

said first transfer processing part transfers the data received fromsaid second terminal to said first terminal and the data received fromsaid first terminal to said second terminal.

(Configuration Example in the Second Embodiment)

According to the second embodiment, a communication system has a firstserver (SOAP-SIP adapter 6 a), a device (SOAP-SIP adapter 6 b) formaking an establishment of connection with said first server in a SIPprotocol, and a first terminal (terminal Ala, Client A) forcommunicating with said first server, said first server comprises:

an interface (SOAP control part) for receiving a connection requestmessage (SOAP connectRequest);

a processing part (SPCC module part, SIP control part) for making theestablishment of connection with said device in said SIP protocol inaccordance with said received connection request message; and

a first transfer control part (media stream control part) fortransferring data received from said first terminal to said device afterthe establishment of connection by said processing part.

The communication system described above further comprises a secondterminal (terminal B7 b, Client B),

said device is a third server (SOAP-SIP adapter server 6 b) having asecond transfer processing part (media stream control part 5103 b), and

said second transfer processing part receives said data transferred fromsaid first transfer control part and transfers said data to said secondterminal

The present invention is applicable to the network such as an NGN, forexample.

What is claimed is:
 1. A first server configured to substituteestablishment of a session for making a media stream communicationbetween a plurality of terminals, via a second server existing in anetwork in which it is required that IP addresses for establishingsignaling channel and data channel are the same, the first servercomprising: a processor configured to: receive, from the second server,a connection request message including a plurality of Session InitiationProtocol-Uniform Resource Identifiers (SIP-URIs) corresponding toidentifiers of a plurality of terminals to be connected for making amedia stream communication, the connection request message beinginputted to the second server from a terminal of a user of a thirdparty; establish connections with the plurality of terminals based onthe received connection request message including a plurality ofSIP-URIs corresponding to the identifiers of the plurality of terminals,and generate a session ID concerning of the plurality of terminals basedon the connection request message; a memory storage configured to storeinformation concerning the media stream communication, including thesession ID, a media stream sending/receiving IP address which is an IPaddress of the first server, a plurality of partner IP addresses whichare IP addresses of the plurality of terminals to be connected; and acontrol part configured to: receive data after establishment of theconnection, the received data including a first sender which is one ofthe terminal to be connected and a first destination which is the firstserver; specify the another terminal to be connected associated with thefirst sender by referring to the memory storage; and transfer the datato the another terminal, the transferred data including a second senderwhich is the first server and a second destination which is the anotherterminal.
 2. The first server according to claim 1, wherein theidentifier includes an IP address and a port number, wherein the controlpart is configured to: receive the data after establishment of theconnection, the received data including a first sender which is aterminal IP address and a terminal port number, and a first destinationwhich is a first server IP address and a first server port number;specify another terminal IP address and another terminal port numberassociated with the first sender by referring to the memory storage; andtransfer the data to the another terminal, the transferred dataincluding the second sender which is the first server IP address and thefirst server port number, and the second destination which is theanother terminal IP address and the another terminal port number.
 3. Thefirst server according to claim 2, wherein the processor is configuredto establish the connection with the terminal in a SIP protocol.
 4. Thefirst server according to claim 2, wherein the processor is configuredto send a pseudo RBT (Ringing Back Tone) to the terminal to be connectedafter the establishment of the connection with the terminal to beconnected and during setting the connection between the another terminaland the first server.
 5. A communication system having a first serverconfigured to substitute establishment of a session for making a mediastream communication between a plurality of terminals, via a secondserver existing in a network in which it is required that IP addressesfor establishing signaling channel and data channel are the same, thefirst server comprising: a processor configured to: receive, from thesecond server, connection request message including a plurality ofSession Initiation Protocol-Uniform Resource Identifiers (SIP-URIs)corresponding to identifiers of a plurality of terminals to be connectedfor making a media stream communication, the connection request messagebeing inputted to the second server from a terminal of a user of a thirdparty; establish connections with the plurality of terminals based onthe received connection request message including a plurality SIP-URIscorresponding to identifiers of the plurality of terminals, and generatea session ID concerning sessions of the plurality of terminals based onthe connection request message; a memory storage configured to storeinformation concerning the media stream communication, including thesession ID, a media stream sending/receiving IP address which is an IPaddress of the first server, a plurality of partner IP addresses whichare IP addresses of the plurality of terminals to be connected; and acontrol part configured to: receive data after establishment of theconnection, the received data including a first sender which is one ofthe terminal to be connected and a first destination which is the firstserver; specify the another terminal to be connected associated with thefirst sender by referring to the memory storage; and transfer the datato the another terminal, the transferred data including a second senderwhich is the first server and a second destination which is the anotherterminal.
 6. The communication system according to claim 5, wherein theidentifier includes an IP address and a port number, and wherein thecontrol part is configured to: receive the data after establishment ofthe connection, the received data including a first sender which is aterminal IP address and a terminal port number, and a first destinationwhich is a first server IP address and a first server port number;specify another terminal IP address and another terminal port numberassociated with the first sender by referring to the memory storage; andtransfer the data to the another terminal, the transferred dataincluding the second sender which is the first server IP address and thefirst server port number, and the second destination which is theanother terminal IP address and the another terminal port number.
 7. Thecommunication system according to claim 6, wherein the processor isconfigured to establish the connection with the terminal in a SIPprotocol.
 8. The communication system according to claim 6, wherein theprocessor is configured to send a pseudo RBT (Ringing Back Tone) to theterminal to be connected after the establishment of the connection withthe terminal to be connected and during setting the connection betweenthe another terminal and the first server.
 9. A method of communicationwith a terminal in a communication system having a first serverconfigured to substitute establishment of a session for making a mediastream communication between a plurality of terminals, via a secondserver existing in a network in which it is required that IP addressesfor establishing signaling channel and data channel are the same, themethod comprising: receiving by a processor of the first server, fromthe second server, connection request message including a plurality ofSession Initiation Protocol-Uniform Resource Identifiers (SIP-URIs)corresponding to identifiers of a plurality of terminals to be connectedfor making a media stream communication, the connection request messagebeing inputted to the second server from a terminal of a user of a thirdparty; establishing, by the processor, connections with the plurality ofterminals based on the received connection request message including aplurality SIP-URIs corresponding to identifiers of the plurality ofterminals, and generating, by the processor, a session ID concerningsessions of the plurality of terminals based on the connection requestmessage; storing, in a memory storage, information concerning the mediastream communication, including the session ID, a media streamsending/receiving IP address which is an IP address of the first server,a plurality of partner IP addresses which are IP addresses of theplurality of terminals to be connected; and receiving, by a control partof the first server, data after establishment of the connection, thereceived data including a first sender which is one of the terminal tobe connected and a first destination which is the first server;specifying, by the control part, the another terminal to be connectedassociated with the first sender by referring to the memory storage; andtransferring, by the control part, the data to the another terminal, thetransferred data including a second sender which is the first server anda second destination which is the another terminal.